Support Storybook config directory #878
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For reasons outlined in my PR comment, as well as an internal confluence document, leaning into the standard
.storybook
configuration folder rather than pointing into sku's node modules addresses some issues and reduces the complexity of sku's storybook integration.This includes:
Sku still maintains control over the
.storybook/main.js
file as this contains critical configuration that enables storybook to work with sku's wepback setup, VE, TypeScript, etc.This has been tested internally in both a regular app and an app within a monorepo.